SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 61062: Jobs submitted to SAS® Grid Manager and the batch servers fail after you enable the SAS® Environment Manager APM ETL

DetailsAboutRate It

After you enable the audit, performance, and measurement (APM) extract, transform, load (ETL) process in the SAS Environment Manager Service Architecture, SAS programs that are submitted to the GridServer or BatchServer jobs might fail with messages similar to the following:

ERROR: User does not have privileges for the attempted operation.  File =/opt/sas/config/Lev1/SASApp/GridServer/PerfLogs/arm4_GridServer_2017-09-12_13.31.02_examplehost_24023.log.  System Error Code = 13.
ERROR: Insufficient authorization to access /opt/sas/config/Lev1/SASApp/GridServer/PerfLogs/arm4_GridServer_2017-09-12_13.31.02_examplehost_24023.log.
ERROR: Invalid option value /opt/sas/config/Lev1/SASApp/GridServer/logconfig.apm.connect.xml for SAS option LOGCONFIGLOC.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

ERROR: Invalid option value /opt/sas/config/Lev1/SASApp/BatchServer/logconfig.apm.xml for SAS option LOGCONFIGLOC.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

You might also see exit code 105 for these failed jobs.

To work around this problem:

  1. Ensure that the PerfLogs directory for each server provides Read, Write, and Execute permissions for all users, as follows:
    chmod 777 /opt/sas/config/Lev1/SASApp/BatchServer/PerfLogs

    chmod 777 /opt/sas/config/Lev1/SASApp/GridServer/PerfLogs
  2. To correct a problem where permissions on the PerfLogs directory are reset to 775, make the following changes.
    1. Make a backup copy of the configureAPM.groovy file that resides in the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-client/Scripts/ directory.
    2. Open the configureAPM.groovy file for editing. Note: If this is a multi-machine deployment, update the configureAPM.groovy file on each host in the deployment.
    3. To resolve the BatchServer problem, change false (highlighted below) to true in the createDir() function call that appears in the case 'Perf' section shown below:
      case 'PERF':
         log.info "PERF: $serverContext $serverName"
         if(verbose) term.info "PERF: $serverContext $serverName"
         createDir(thisPath, "PerfLogs", false)
         updateUsermods(usermodspath, force)
         break
    4. To resolve the GridServer problem, change false (highlighted below) to true in the createDir() function call that appears in the case 'Grid' section shown below:
       case 'GRID':
          log.info "GRID: $serverContext $serverName"
          if(verbose) term.info "GRID: $serverContext $serverName"
       // Grid is a special-case. It simply renames/copies existing ARM logconfig files into the appropriate names
       // where they get automatically picked-up by the existing Grid run scripts.
                createDir(thisPath, "PerfLogs", false)
                copySave(thisPath, "logconfig.apm.batch.disable.xml", "logconfig.apm.batch.xml", force, false)
      // don't create the flag file until the second copy is complete in this dir to avoid collision
                    copySave(thisPath, "logconfig.apm.connect.disable.xml", "logconfig.apm.connect.xml", force, true)
                                          break
A fix for this issue is planned for a later software release.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Environment Manager Enablement Kit Server64-bit Enabled Solaris2.22.49.4 TS1M39.4 TS1M5
HP-UX IPF2.22.49.4 TS1M39.4 TS1M5
Linux for x642.22.49.4 TS1M39.4 TS1M5
64-bit Enabled AIX2.22.49.4 TS1M39.4 TS1M5
Solaris for x642.22.49.4 TS1M39.4 TS1M5
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.